InterCD 2000 September/september_2000.iso/intercd/root/^Linux/cfengine-1.5.3/contrib/cron-shell-help-script/text0000.txt

Text File | 1998-07-15 | 5.9 KB | 172 lines

Hi Mark,
hi all!

I would like to contribute the following script "cfcron" to the cfengine
package. Basically it is a sh-script version of cfwrap. I wrote a
README (puh ;-) where everything else is explained.

If anybody has any problems running this script please send me a
mail. I wrote it primarily for SunOS 4.1.x and Solaris, so if it doesn't
work on other platforms you might have to do some minor changes or drop
me a mail, too.

Here we go, first the README, then the script. Hope you find it useful.

Cheers
    Uwe

------------------------cfcron.README-----------------------------------------
    cfcron vers. 1.3

cfcron is a wrapper script, which helps using CFengine from within
cron. The output of a CFengine run will be mailed to the sysadmin only
if it has changed, at least once a day. This script is more or less
based on cfwrap which was written in perl by Mark Burgess. But I don't
have perl around on all platforms, so I needed a shell script. Also
this script has some features which are not found in cfwrap.

Before using cfcron you should adopt some variables at the
beginning of the script (pathes etc.)

I think a short example will describe the usage best.

Suppose you have your cfengine scripts in a central repository
which you mount to different hosts by NFS, let's say
/usr/local/etc/cfe. You might consider to put cfcron in
/usr/local/etc. Now you can put an entry into all the crontab's
on all that hosts like this:
11 * * * * [ -x /usr/local/etc/cfe/cfcron ] && /usr/local/etc/cfe/cfcron

This entry will run CFengine ones per hour and mail you the
results (if they have changed). Everything normal until here.
But if you want to stop running CFengine on all hosts (e.g. for
some testing) you normally have to rename the script or remove the
crontab entries. Another way is the one I use in this script: there
is a global stop file, "noconf" e.g. in /usr/local/etc/cfe. This
file prohibits the running of CFengine if it exists. So for the
example above you just have to do a "touch /usr/local/etc/cfe/noconf"
and you are done, cfcron will exit silently from now on.

Sometimes you might want to stop the execution of CFengine on just
one host. For that reason (and for those guys starting every script
lying around ;-) cfcron uses another file which permits the running
of CFengine. It looks for a file named ".ok" in the current directory,
which is if cfcron is run by cron the homedir of the crontab owner
(in most cases root). But if cfcron is started accidently, one will
(hopefully) not be in the home directory. So this mechanism might be
helpful to avoid running a complete CFengine job by mistake. If the
ok file does not exist cfcron will send a mail that it is disabled.

In system administration CFengine does a great job, but it could be
pretty dangerous too, cause it can do a lot of damage if not used
careful, especially if you let it run by cron. With those
possibilities described above it might be a bit more safely to let it
run automatically on a bigger no. of hosts.

So many words for such a small script...

Uwe Sievers, <[e-mail]>, 1998
------------------------cfcron-----------------------------------------------
#!/bin/sh
##############################################################
#
# wrapper script, mails output if there is any (and if changed)
# Mainly intended for running cfengine; more or less based on
# cfwrap which is written in perl. Also this one has some
# "enhancements" (see the README).
#
# (us) 21-12-97 v1.1
# (us) 23-12-97 v1.2 ok-file permits execution (local)
#             noconf prohibits execution (global)
#             on all hosts (silent)
# (us) 24-12-97 v1.3 Fixed: mail problem if error in cfe-script (could
#                    not find sysadmin)
#
# Solaris Version & SunOS
#
# Copyright (c) Uwe Sievers 1997/98    <[e-mail]>
# GPL rules, vers. 2 or newer. Use this program at your own risk!
##############################################################
#
#----------------------- adopt to your needs ----------------------
FILECF="/usr/local/etc/cfe/cron/cron.cf"
CFENGINE=/usr/local/sbin/cfengine
TMPFILE=/var/tmp/cfwrap.$$
OLDFILE=/var/tmp/cfwrap.o
NOCONF=/usr/local/etc/noconf
USER=`/usr/ucb/whoami`
HOST=`/usr/bin/hostname`
MAILER=/usr/bin/mailx
#------------------no changes should be nessesary below (hopefully)
COMM="$CFENGINE -f $FILECF"
SYSV=
BSD=
OK=


#cfe Vars
OSREL=`uname -r`
OSVERS=`uname -s`
export OSREL OSVERS

if [ "$USER" != "root" ] ; then
    echo "Bad luck, only root can run this one!"
    $MAILER -s "$USER tried to run cfcron on $HOST" root </dev/null
    exit 1
fi

# just a hook
if [ $OSVERS = SunOS -a $OSREL -lt 5 ] ; then
#    echo BSD
    :
else
#    echo SYSV
    :
fi

if [ -f $NOCONF ] ; then        # exit silently
    exit 1
fi

if [ -f .ok ] ; then
    OK=true
else
    COMM=/bin/true
    unset OK
#    exit 0
fi

# does not work in case of error in cfe script
#SYSADM=`$CFENGINE -a -S -w -f $FILECF 2>/dev/null`

SYSADM=`egrep '^[^#].*sysadm.*=' $FILECF | cut -f2 -d\( | cut -f1 -d\)`

SUBJECT="cfengine on $HOST start at `date`"

echo "This message originates from host $HOST on `date '+%d.%m.%y'`" \
                        >> $TMPFILE
if [ -n "$OK" ] ; then
    echo "The full command issued was: $COMM"   >> $TMPFILE
else
    echo "d i s a b l e d"            >> $TMPFILE
fi

[ -n "$OK" ] && $COMM >>$TMPFILE 2>&1

# only send mail if anything changes
/usr/bin/diff $TMPFILE $OLDFILE >/dev/null ||
    $MAILER -s "$SUBJECT" $SYSADM < $TMPFILE

rm $OLDFILE
mv $TMPFILE $OLDFILE
chmod 600 $OLDFILE
exit 0
--------------------------end----------------------------------------
--
________      ____Deutsche Welle Berlin radio & tv broadcasting________
   | \  \    /    Uwe Sievers        (system administrator)
   | /   \/\/     <[e-mail]>    Tel.: [phone]
=========================USENET is *not* the non-clickable part of WWW!